Sharing of portable initialized objects between computing platforms

ABSTRACT

A sub-process is performed on a first computing platform to create a portable initialized object. The portable initialized object is communicated to a second computing platform. The second computing platform uses the portable initialized object to replace performing the sub-process.

BACKGROUND

The present disclosure relates generally to the field of data transferbetween computing platforms and more particularly to transfer ofinitialized objects between computing platforms.

The use of virtual machine technology (VM) in cloud computing and otherenvironments is on the rise. VM technology is useful for custompackaging and execution of operating systems. As the user's needs withina VM change, the package can be configured to meet the user's needs. Oneaspect of expense in the processing of VM's is the ongoing time cost ofinvoking a VM, which typically includes the initialization stepsrequired to boot-up the underlying operating system, as well as theapplication of new and ongoing maintenance applied to VM as it isrunning.

SUMMARY

Disclosed herein are embodiments of a method for bypassing a sub-processon a first computing platform. The method includes receiving, from asecond computing platform, a portable initialized object. The portableinitialized object was generated by execution of the sub-process on thesecond computing platform. The method further includes using theportable initialized object to replace performing the sub-process.

Also disclosed herein are embodiments of a method for sharing a portableinitialized object by a first computing platform. The method includesexecuting a sub-process to generate the portable initialized object andcommunicating the portable initialized object to a second computingplatform. The portable initialized object is configured to replaceperformance of the sub-process in the second computing platform.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a flow diagram of an example method for sharing an inletby a computing platform.

FIG. 2 depicts a flow diagram of an example method for using an inlet tobypass a sub-process on a computing platform.

FIG. 3 depicts a flow diagram of an example method for sharing an outletby a computing platform.

FIG. 4 depicts a flow diagram of an example method for using an outletto bypass a sub-process on a computing platform.

FIG. 5 depicts an example flow diagram of the creation of inlets in a VMduring initialization.

FIG. 6 depicts an example flow diagram of the creation of an outlet by aVM.

FIG. 7 depicts a high level block diagram of an example system forsharing portable initialized objects between computing systems.

FIG. 8 depicts a schematic of an example of a cloud computing node.

FIG. 9 depicts an illustrative cloud computing environment.

FIG. 10 depicts a set of functional abstraction layers provided by cloudcomputing environment.

DETAILED DESCRIPTION

In this detailed description, reference is made to the accompanyingdrawings, which illustrate example embodiments. It is to be understoodthat other embodiments may be utilized and structural changes may bemade without departing from the scope of the disclosure. The terminologyused herein is for the purpose of describing particular embodiments onlyand is not intended to be limiting. In accordance with disclosedfeatures, a method, system, and computer program product are providedfor sharing portable initialized objects between computing platforms.

Embodiments of the current invention provide methods which may lower thetime spent processing certain sequences in the boot-up process of acomputing platform, and may also lower the time spent performing ongoingmaintenance of computing platforms that are executing in close networkpeer-to-peer proximity to each other. For the purposes of thisapplication the term “inlet” will refer to portable initialized objectscreated by a sub-process during the boot-up process and the term“outlet” will refer to portable initialized objects created by asub-process during application of updates.

When an operating system on a computing platform begins the boot-upprocess, the sequence of events comprises initialization of a series ofdata structures, devices, and the like. Once the operating system isinitialized, a user interface is displayed, typically a logon challenge,and the operating system is ready for a user to log in and begin usingthe system. During this boot up process multiple initializationsub-processes can be identified based on the time required to performthe sub-processes. Inlets created during these sub-processes may be madeavailable to another computing platform which is in the boot-up process.The other computing platform may use the inlets to avoid performing thesub-processes, which may result in a faster boot up.

For example, when initializing the TCP/IP configuration, there is a timeconsuming process of reading and XML parsing the TCP/IP configurationinto a Document Object Model (DOM). This sub-process may be isolatedinto an inlet for a VM configuration. Once the initialization of the DOMis complete, it may be shared with other VM's. As part of the inlettransfer process, the DOM may be placed in a memory block, and the offerto use the DOM posted by the VM. Then other VM's in close peer networkproximity can transfer the DOM already pre-parsed to their VM and beginusing the DOM. The second VM saves the time of loading and parsing theXML document. Close peer network proximity includes mechanisms likeBluetooth, Near Field Communication (NFC), peer-to-peer 802.11 wifi,wifi direct, or other means where the two VM's can communicate directly.The use of close peer network connections may limit the usage andbandwidth of the larger non-peer connected networks.

In another embodiment, a computing platform in a “booting-up” state maybe broadcasting inlets at a particular location where many computingplatforms are booting up. For example, a computing platform producingand sharing inlets could be used at an airport terminal where manycomputers are booting-up on a recently landed plane. These inlets mayalso contain an advertisement which is displayed on the computing systemwhich receives the inlet.

A similar method may be applied to updates for computing platforms. Acomputing platform may download and unpack an update to create anoutlet. However, the computing platform may process and apply the outletat the time of creation (or transfer), or it may be processed andapplied at a later time such as when the computing platform is beingterminated.

For example, a VM may receive a critical update notice. The VM maydownload and unpack the critical update to create an outlet. The VM mayprocess and apply the outlet at creation or at a later time. The VM maymake the outlet available to other VM's of the same or similarconfiguration which may also apply the update. Then other VM's in closepeer network proximity can transfer the DOM already pre-parsed to theirVM and begin using the DOM. The second VM saves the time of downloadingthe update from a server and unpacking of the update. Close peer networkproximity includes mechanisms like Bluetooth, near field communication(NFC), peer-to-peer 802.11 wifi, wifi direct, or other means where thetwo VM's can communicate directly. The use of close peer networkconnections may limit the usage and bandwidth of the larger non-peerconnected networks.

Identification of inlets and outlets may be provided in several ways. Insome embodiments this will be handled with a naming system that namesthe inlet or outlet and the maintenance level of the inlet or outletusing a composite hash tag. In some embodiments, the identification willinclude information encoded in the ID value to allow inlets and outletsto be applied in a specific order. The receiving VM will understand thenaming system, and queue and hold any number of inlets or outlets untilthey can be applied to the VM in proper order.

Security for sharing inlets and outlets may be provided in several ways.In some embodiments this will be handled with a naming system that namesthe inlet or outlet and the maintenance level of the inlet or outletusing a composite hash tag. In some embodiments, the computing systemsmay require authorization to share which may include using a list ofauthorized users or computing platforms which may be edited by a systemadministrator. In some embodiments, a computing platform may beauthorized if it is located in an acceptable location. The location maybe determined through GPS or any other method. Other security mechanismsmay also be employed.

Referring now to FIG. 1, a flow diagram 100 of an example method forsharing an inlet by a computing platform is depicted. At step 110, thecomputing platform starts system initialization. The computing platformmay be any computing platform such as a virtual machine, logicalpartition, or hardware based non-virtual machine. At step 120, thecomputing platform performs a sub-process to generate a portableinitialized object (inlet). At step 130, the computing platform assignsan ID to the inlet. The ID may indicate which sub-process the inlet isassociated with. At step 140, a time out value is assigned to the inlet.The time out value may represent when the computing platform shoulddiscard the inlet. At step 150, the inlet is made available to othercomputing platforms. An offer to use the inlet may be posted by thecomputing platform. The computing platform may communicate the inlet toa second computing platform which is initializing. This communicationmay occur through a peer-to-peer network. The peer-to-peer network maybe a connection where the two computing platforms communicate directly,such as Bluetooth, Near Field Communication, peer-to-peer 802.11 wifi,or wifi direct.

At step 160, the computing platform determines if the time out value hasbeen reached for the inlet. If the time out value has not been reached,the computing platform may return to step 150 and continue to make theinlet available. If the computing platform detects that the time outvalue has been reached, the computing platform may continue to step 170and discard the inlet.

FIG. 2 depicts a flow diagram 200 of an example method for using aninlet to bypass a sub-process on a computing platform. At step 210, afirst computing platform starts system initialization. The firstcomputing platform may be any computing platform such as a virtualmachine, logical partition, or hardware based non-virtual machine. Atstep 220, the first computing platform receives a portable initializedobject (inlet) from a second computing platform. The inlet may have beenproduced by a sub-process performed by the second computing platform.The inlet may be received through a peer-to-peer network. Thepeer-to-peer network may be a connection where the two computingplatforms communicate directly, such as Bluetooth, Near FieldCommunication, peer-to-peer 802.11 wifi, or wifi direct. At step 230,the inlet is used by the first computing platform to replace performanceof the sub-process during initialization. At step 240, the firstcomputing platform makes the inlet available to other computingplatforms.

FIG. 3 depicts a flow diagram 300 of an example method for sharing anoutlet by a computing platform. At step 310, the computing platformreceives an update notification. The computing platform may be anycomputing platform such as a virtual machine, logical partition, orhardware based non-virtual machine. At step 320, the computing platformdownloads the update. At step 330, the computing platform performs asub-process related to the update to generate a portable initializedobject (outlet). At step 340, the computing platform assigns an ID tothe outlet. The ID may indicate which sub-process the outlet isassociated with or which update the outlet is associated with. At step350, a time out value is assigned to the outlet. The time out value mayrepresent when the computing platform should discard the outlet. At step360, the outlet is made available to other computing platforms. An offerto use the outlet may be posted by the computing platform. The computingplatform may communicate the outlet to a second computing platform whichis initializing. This communication may occur through a peer-to-peernetwork. The peer-to-peer network may be a connection where the twocomputing platforms communicate directly, such as Bluetooth, Near FieldCommunication, peer-to-peer 802.11 wifi, or wifi direct.

At step 370, the computing platform determines if the time out value hasbeen reached for the outlet. If the time out value has not been reached,the computing platform may return to step 360 and continue to make theoutlet available. If the computing platform detects that the time outvalue has been reached, the computing platform may continue to step 380and discard the outlet.

FIG. 4 depicts a flow diagram 400 of an example method for using anoutlet to bypass a sub-process on a computing platform. At step 410, afirst computing platform receives an update notification. The firstcomputing platform may be any computing platform such as a virtualmachine, logical partition, or hardware based non-virtual machine. Atstep 420, the first computing platform receives a portable initializedobject (outlet) from a second computing platform. The outlet may havebeen produced by a sub-process performed by the second computingplatform. This portable object may be used by the first computingplatform in lieu of the first computing platform downloading andinitializing the update separately. The outlet may be received through apeer-to-peer network. The peer-to-peer network may be a connection wherethe two computing platforms communicate directly, such as Bluetooth,Near Field Communication, peer-to-peer 802.11 wifi, or wifi direct. Atstep 430, the outlet is used by the first computing platform to replaceperformance of the sub-process in applying the update. At step 440, thefirst computing platform makes the outlet available to other computingplatforms.

FIG. 5 depicts an example flow diagram of the creation of inlets in a VMduring initialization. Blocks 510, 515, and 520 represent threeprocesses performed by the VM during initialization. Block 510represents the process of initializing the operating system kernelstatic data. Block 530 represents the sub-process of reading andbuilding the kernel data into memory. The sub-process produces an inlet,the kernel data block. Block 500 represents the VM making the kerneldata block available to other VM's with an ID of 101. The ID mayindicate the other VM's which sub-process the inlet is associated with.The VM may communicate the kernel data block via peer-to-peer network toother VM's in network proximity that are also in the initializationphase.

Block 515 represents the process of initializing TCP/IP Configuration.Block 535 represents the sub-process of reading and building TCP/IP XMLConfiguration into a document object model (DOM). The sub-processcreates an inlet, the TCP/IP Configuration DOM. Block 505 represents theVM making the TCP/IP Configuration DOM available to other VM's with anID of 102. The ID may indicate the other VM's which sub-process theinlet is associated with, or may indicate that this inlet is used afterthe inlet with ID 101. The VM may communicate the TCP/IP ConfigurationDOM via peer-to-peer network to other VM's in network proximity that arealso in the initialization phase.

Block 520 represents a third initialization process. The processincludes a sub-process which creates an inlet. Block 525 represents theVM making the inlet available with an ID of 103. The ID may indicate theother VM's which sub-process the inlet is associated with, or mayindicate that this inlet is used after the inlets with ID's 101 and 102.The VM may communicate the TCP/IP Configuration DOM via peer-to-peernetwork to other VM's in network proximity that are also in theinitialization phase.

FIG. 6 depicts an example flow diagram of the creation of an outlet by aVM. Block 610 represents the VM executing processes. Block 615represents the VM receiving a critical service update notification andthe process of applying the update. Block 625 represents the sub-processof downloading and unpacking the critical update. The sub-processcreates an outlet, the unpacked critical update package. Block 605represents the VM making the unpacked critical update package availableto other VM's. The VM may communicate the unpacked critical updatepackage via peer-to-peer network to other VM's in network proximity thatare also in the initialization phase. Block 620 represents the VMcontinuing to execute processes.

FIG. 7 depicts a high level block diagram of an example system 700 forsharing portable initialized objects between computing systems. FourVM's 720 a-d are connected to cloud computing environment 710 for use ofat least some of the computing resources of cloud 710. VM 720 a is incommunication with VM 720 b via a peer-to peer network. VM's 720 a and720 b may be in close network peer-to-peer proximity to each otherusing, for example, Bluetooth, Near Field Communication (NFC),peer-to-peer 802.11 wifi, or wifi direct. Inlets and outlets may betransferred between VM's 720 a and 720 b via the peer-to-peer network.VM's 720 c and 720 d are similarly in communication with each other viaa peer-to-peer network. However, VM's 720 c-d are not in peer-to-peercommunication with VM's 720 a-b. This may be because they are not inclose enough proximity to each other to use close peer-to-peer networkssuch as Bluetooth, Near Field Communication, peer-to-peer 802.11 wifi,or wifi direct. Although the VM's shown are only in peer-to-peercommunication with one other VM, they may be in peer-to-peercommunication with any number of VM's.

It is understood in advance that although this disclosure includes adetailed description on cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 8, a schematic of an example of a cloud computingnode is shown. Cloud computing node 10 is only one example of a suitablecloud computing node and is not intended to suggest any limitation as tothe scope of use or functionality of embodiments of the inventiondescribed herein. Regardless, cloud computing node 10 is capable ofbeing implemented and/or performing any of the functionality set forthhereinabove.

In cloud computing node 10 there is a computer system/server 12, whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 12 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 12 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 8, computer system/server 12 in cloud computing node 10is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 12 may include, but are not limitedto, one or more processors or processing units 16, a system memory 28,and a bus 18 that couples various system components including systemmemory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnect (PCI) bus.

Computer system/server 12 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 12, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 30 and/or cachememory 32. Computer system/server 12 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 18 by one or more datamedia interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 40, having a set (at least one) of program modules 42,may be stored in memory 28 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 42 generally carry out the functions and/ormethodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more externaldevices 14 such as a keyboard, a pointing device, a display 24, etc.;one or more devices that enable a user to interact with computersystem/server 12; and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 12 to communicate with one or moreother computing devices. Such communication can occur via Input/Output(I/O) interfaces 22. Still yet, computer system/server 12 cancommunicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 20. As depicted, network adapter 20communicates with the other components of computer system/server 12 viabus 18. It should be understood that although not shown, other hardwareand/or software components could be used in conjunction with computersystem/server 12. Examples, include, but are not limited to: microcode,device drivers, redundant processing units, external disk drive arrays,RAID systems, tape drives, and data archival storage systems, etc.

Referring now to FIG. 9, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 9 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 10, a set of functional abstraction layersprovided by cloud computing environment 50 (FIG. 9) is shown. It shouldbe understood in advance that the components, layers, and functionsshown in FIG. 10 are intended to be illustrative only and embodiments ofthe invention are not limited thereto. As depicted, the following layersand corresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include mainframes, in oneexample IBM® zSeries® systems; RISC (Reduced Instruction Set Computer)architecture based servers, in one example IBM pSeries® systems; IBMxSeries® systems; IBM BladeCenter0 systems; storage devices; networksand networking components. Examples of software components includenetwork application server software, in one example IBM WebSphere®application server software; and database software, in one example IBMDB2 database software. (IBM, zSeries, pSeries, xSeries, BladeCenter,WebSphere, and DB2 are trademarks of International Business MachinesCorporation registered in many jurisdictions worldwide).

Virtualization layer 62 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers;virtual storage; virtual networks, including virtual private networks;virtual applications and operating systems; and virtual clients.

In one example, management layer 64 may provide the functions describedbelow. Resource provisioning provides dynamic procurement of computingresources and other resources that are utilized to perform tasks withinthe cloud computing environment. Metering and Pricing provide costtracking as resources are utilized within the cloud computingenvironment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal provides access to the cloud computing environment forconsumers and system administrators. Service level management providescloud computing resource allocation and management such that requiredservice levels are met. Service Level Agreement (SLA) planning andfulfillment provide pre-arrangement for, and procurement of, cloudcomputing resources for which a future requirement is anticipated inaccordance with an SLA.

Workloads layer 66 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation; software development and lifecycle management; virtualclassroom education delivery; data analytics processing; transactionprocessing; and mobile desktop.

Embodiments described herein may be in the form of a system, a method,or a computer program product. Accordingly, aspects of embodiments ofthe invention may take the form of an entirely hardware embodiment, anentirely program embodiment (including firmware, resident programs,micro-code, etc., which are stored in a storage device) or an embodimentcombining program and hardware aspects that may all generally bereferred to herein as a “circuit,” “module,” or “system.” Further,embodiments of the invention may take the form of a computer programproduct embodied in one or more computer-readable medium(s) havingcomputer-readable program code embodied thereon.

Any combination of one or more computer-readable medium(s) may beutilized. The computer-readable medium may be a computer-readable signalmedium or a computer-readable storage medium. A computer-readablestorage medium, may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (an non-exhaustive list) of the computer-readablestorage media may comprise: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random access memory(RAM), a read-only memory (ROM), an erasable programmable read-onlymemory (EPROM) or Flash memory, an optical fiber, a portable compactdisc read-only memory (CD-ROM), an optical storage device, a magneticstorage device, or any suitable combination of the foregoing. In thecontext of this document, a computer-readable storage medium may be anytangible medium that can contain, or store, a program for use by or inconnection with an instruction execution system, apparatus, or device.

A computer-readable signal medium may comprise a propagated data signalwith computer-readable program code embodied thereon, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer-readable signal medium may be any computer-readable medium thatis not a computer-readable storage medium and that communicates,propagates, or transports a program for use by, or in connection with,an instruction execution system, apparatus, or device. Program codeembodied on a computer-readable medium may be transmitted using anyappropriate medium, including but not limited to, wireless, wire line,optical fiber cable, Radio Frequency, or any suitable combination of theforegoing.

Embodiments of the invention may also be delivered as part of a serviceengagement with a client corporation, nonprofit organization, governmententity, or internal organizational structure. Aspects of theseembodiments may comprise configuring a computer system to perform, anddeploying computing services (e.g., computer-readable code, hardware,and web services) that implement, some or all of the methods describedherein. Aspects of these embodiments may also comprise analyzing theclient company, creating recommendations responsive to the analysis,generating computer-readable code to implement portions of therecommendations, integrating the computer-readable code into existingprocesses, computer systems, and computing infrastructure, metering useof the methods and systems described herein, allocating expenses tousers, and billing users for their use of these methods and systems. Inaddition, various programs described hereinafter may be identified basedupon the application for which they are implemented in a specificembodiment of the invention. But, any particular program nomenclaturethat follows is used merely for convenience, and thus embodiments of theinvention are not limited to use solely in any specific applicationidentified and/or implied by such nomenclature. The exemplaryenvironments are not intended to limit the present invention. Indeed,other alternative hardware and/or program environments may be usedwithout departing from the scope of embodiments of the invention.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

What is claimed is:
 1. A method for bypassing a sub-process on a firstcomputing platform, the method comprising: receiving, from a secondcomputing platform, a portable initialized object, the portableinitialized object generated by execution of the sub-process on thesecond computing platform; and using the portable initialized object toreplace performing the sub-process.
 2. The method of claim 1, whereinthe first computing platform is selected from the group consisting of afirst virtual machine, a first logical partition, and a first hardwarebased non-virtual machine, and wherein the second computing platform isselected from the group consisting of a second virtual machine, a secondlogical partition, and a second hardware based non-virtual machine. 3.The method of claim 1, wherein the first computing platform is a virtualmachine.
 4. The method of claim 1, wherein the portable initializedobject is received through a peer-to-peer network.
 5. The method ofclaim 4, wherein the first computing platform and the second computingplatform communicate directly through the peer-to-peer network.
 6. Themethod of claim 5, wherein the peer-to-peer network is selected from thegroup consisting of Bluetooth, Near Field Communication, peer-to-peer802.11 wifi, and wifi direct.
 7. The method of claim 1, wherein thesub-process is selected from the group consisting of an initializationsub-process and an update sub-process.
 8. The method of claim 1, furthercomprising: communicating the portable initialized object to a thirdcomputing platform.
 9. The method of claim 1, further comprising:determining that the first computing platform is authorized to receivethe portable initialized object.
 10. The method of claim 9, wherein thedetermining that the first computing platform is authorized to receivethe portable initialized object comprises: determining that the firstcomputing platform is at an acceptable location.
 11. A method forsharing a portable initialized object by a first computing platform, themethod comprising: executing a sub-process to generate the portableinitialized object; and communicating the portable initialized object toa second computing platform, the portable initialized object configuredto replace performance of the sub-process in the second computingplatform.
 12. The method of claim 11, wherein the first computingplatform is selected from the group consisting of a first virtualmachine, a first logical partition, and a first hardware basednon-virtual machine, and wherein the second computing platform isselected from the group consisting of a second virtual machine, a secondlogical partition, and a second hardware based non-virtual machine. 13.The method of claim 11, wherein the second computing platform is avirtual machine.
 14. The method of claim 11, wherein the portableinitialized object is communicated through a peer-to-peer network. 15.The method of claim 14, wherein the first computing platform and thesecond computing platform communicate directly through the peer-to-peernetwork.
 16. The method of claim 15, wherein the peer-to-peer network isselected from the group consisting of Bluetooth, Near FieldCommunication, peer-to-peer 802.11 wifi, and wifi direct.
 17. The methodof claim 11, wherein the sub-process is selected from the groupconsisting of an initialization sub-process and an update sub process.18. The method of claim 11, further comprising: associating a time outvalue with the portable initialized object; and discarding the object inresponse to detecting the time out value has been reached.
 19. Themethod of claim 11, further comprising: determining that the secondcomputing platform is authorized to receive the portable initializedobject.
 20. The method of claim 19, wherein the determining that thesecond computing platform is authorized to receive the portableinitialized object comprises: determining that the second computingplatform is at an acceptable location.